Skip to content

soc: arm: st_stm32: h7: support DT-defined MPU regions #45970

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

soc: arm: st_stm32: h7: support DT-defined MPU regions #45970

wants to merge 1 commit into from

Conversation

@GeorgeCGV
Copy link
Contributor

@GeorgeCGV GeorgeCGV commented May 24, 2022 •
edited
Loading

Adds the ability to define MPU regions in the DTS.

Some MCUs (i.e. H730) require the MPU region to be configured before it's used (e.g. FMC PSRAM).

In combination with #45969, it is possible to configure the required MPU region for the FMC on
H730 MCU so that the FMC could be used with an external display.

For example:

	fmc_ext_mem: fmc_ext_mem@64000000 {
		compatible = "zephyr,memory-region", "mmio-sram";
		reg = <0x64000000 DT_SIZE_M(64)>;
		zephyr,memory-region = "PSRAM2";
		zephyr,memory-region-mpu = "IO";
	};

@GeorgeCGV
soc: arm: st_stm32: h7: support DT-defined MPU regions
3c5ff86 
Adds the ability to define MPU regions in the DTS.

Some MCUs (i.e. H730) require the MPU region to be
configured before it's used (e.g. FMC PSRAM).

Signed-off-by: Georgij Cernysiov <[email protected]>
@GeorgeCGV GeorgeCGV added the platform: STM32 ST Micro STM32 label May 24, 2022
@GeorgeCGV GeorgeCGV requested a review from erwango as a code owner May 24, 2022 15:37
@erwango erwango added this to the v3.2.0 milestone May 24, 2022
@zephyrbot zephyrbot requested review from ABOSTM, FRASTM and gmarull May 24, 2022 19:46
@GeorgeCGV GeorgeCGV mentioned this pull request May 25, 2022
Merged
@erwango
Copy link
Member

erwango commented Jun 29, 2022

Fixed by #46663

@erwango erwango closed this Jun 29, 2022
@GeorgeCGV
Copy link
Contributor Author

GeorgeCGV commented Jun 29, 2022

Why not merge existing and older PRs? I don't mind as changes are identical.

@erwango
Copy link
Member

erwango commented Jun 29, 2022

Why not merge existing and older PRs? I don't mind as changes are identical.

Sorry, sometime it's hard to always treat incoming PR queue as FIFO.
Sometime you just treat the ones on top like in a mailbox for instance.

@aurel32
Copy link
Contributor

aurel32 commented Jun 29, 2022

Why not merge existing and older PRs? I don't mind as changes are identical.

Sorry, it appears that I didn't check very well the existing PR before submitting #46663.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@erwango erwango Awaiting requested review from erwango

@ABOSTM ABOSTM Awaiting requested review from ABOSTM

@FRASTM FRASTM Awaiting requested review from FRASTM

@gmarull gmarull Awaiting requested review from gmarull

Assignees

@erwango erwango

Labels

platform: STM32 ST Micro STM32

Projects

None yet

Milestone

v3.2.0

Development

Successfully merging this pull request may close these issues.

3 participants

@GeorgeCGV @erwango @aurel32